release: 0.2.0 - #2
Open
kernel-internal[bot] wants to merge 2 commits into
Open
Conversation
Stainless-Generated-From: cbc546d01211970ac7bc195f0b260106aad040a8
sjmiller609
approved these changes
Aug 21, 2026
sjmiller609
left a comment
sjmiller609
left a comment
There was a problem hiding this comment.
TTL and expiration SDK generation verified.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.2.0 (2026-08-21)
Features
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Note
Low Risk
Generated SDK surface and version bump only; no auth, transport, or client runtime changes. Expiration is optional and mutually exclusive at the API layer.
Overview
Releases 0.2.0 and exposes instance auto-expiration on create/update.
Callers can set mutually exclusive
ttl(Go duration) orexpires_at(ISO8601 datetime) when creating or updating instances. TheInstancemodel now includes optionalexpires_at(cleared on fork). Update docs note TTL is relative to the update commit and rejected after the current deadline.Reviewed by Cursor Bugbot for commit 284241f. Bugbot is set up for automated code reviews on this repo. Configure here.